Hi All

Every time I run Visio 2007 software, the wizard installation opens.

When I click on "cancel" the wizard window closed and then the Visio software opens.

I am using with win7 64bit.

Any  information would be appreciated 

thank in advance

Hi,

Try the following steps:

Create a new domain account, add to domain admins, log on using this account, launch VISIO. Rename the profile, then log back. Copy all data from old profile and done.

Similar case here to reference:

http://social.technet.microsoft.com/Forums/en-US/officesetupdeploy/thread/e9846854-58a8-4fda-924c-2eeb96dab149

I too had the same problem on one of our machines - what I found is that I had to go though a number of different registry keys in HKEY_CLASSES_ROOT and modify all of them so they no longer pointed to the visio viewer. Once I had removed all instances pointing to viewer I found that it was then working again. Here is a list of my keys and their settings that got rid of the issue:

.vsd - (default) Visio.Drawing.11

        Content Type  application/vnd.visio

.vsl - (default) Visio.AddOn.11

        Content Type  application/vnd.visio

.vss - (default) Visio.Stencil.11

        Content Type  application/vnd.visio

.vst - (default) Visio.Template.11

        Content Type  application/vnd.visio

.vsu - (default) Visio.CustomUI.11

        Content Type  application/vnd.visio

.vsw - (default) Visio.Workspace.11

        Content Type  application/vnd.visio

.vsx - (default) Visio.Stencil.11

        Content Type  application/vnd.visio

.vtx - (default) Visio.Template.11

        Content Type  application/vnd.visio

I Hope this helps resolve the issue if like me the originally posted fix doesn't resolve the issue. Please remember that editing the registry is not to be done without understanding the risks involved & that if you're not careful you can cause irreversible damage to your system. As such I accept to no Liability for the information contained with this post.

• Proposed as answer by MDL2 5 hours 47 minutes ago

I too had the same problem on one of our machines - what I found is that I had to go though a number of different registry keys in HKEY_CLASSES_ROOT and modify all of them so they no longer pointed to the visio viewer. Once I had removed all instances pointing to viewer I found that it was then working again. Here is a list of my keys and their settings that got rid of the issue:

.vsd - (default) Visio.Drawing.11

        Content Type  application/vnd.visio

.vsl - (default) Visio.AddOn.11

        Content Type  application/vnd.visio

.vss - (default) Visio.Stencil.11

        Content Type  application/vnd.visio

.vst - (default) Visio.Template.11

        Content Type  application/vnd.visio

.vsu - (default) Visio.CustomUI.11

        Content Type  application/vnd.visio

.vsw - (default) Visio.Workspace.11

        Content Type  application/vnd.visio

.vsx - (default) Visio.Stencil.11

        Content Type  application/vnd.visio

.vtx - (default) Visio.Template.11

        Content Type  application/vnd.visio

I Hope this helps resolve the issue if like me the originally posted fix doesn't resolve the issue. Please remember that editing the registry is not to be done without understanding the risks involved & that if you're not careful you can cause irreversible damage to your system. As such I accept to no Liability for the information contained with this post.

• Proposed as answer by MDL2 Friday, April 24, 2015 1:43 AM

I too had the same problem on one of our machines - what I found is that I had to go though a number of different registry keys in HKEY_CLASSES_ROOT and modify all of them so they no longer pointed to the visio viewer. Once I had removed all instances pointing to viewer I found that it was then working again. Here is a list of my keys and their settings that got rid of the issue:

.vsd - (default) Visio.Drawing.11

        Content Type  application/vnd.visio

.vsl - (default) Visio.AddOn.11

        Content Type  application/vnd.visio

.vss - (default) Visio.Stencil.11

        Content Type  application/vnd.visio

.vst - (default) Visio.Template.11

        Content Type  application/vnd.visio

.vsu - (default) Visio.CustomUI.11

        Content Type  application/vnd.visio

.vsw - (default) Visio.Workspace.11

        Content Type  application/vnd.visio

.vsx - (default) Visio.Stencil.11

        Content Type  application/vnd.visio

.vtx - (default) Visio.Template.11

        Content Type  application/vnd.visio

I Hope this helps resolve the issue if like me the originally posted fix doesn't resolve the issue. Please remember that editing the registry is not to be done without understanding the risks involved & that if you're not careful you can cause irreversible damage to your system. As such I accept to no Liability for the information contained with this post.

• Proposed as answer by MDL2 Friday, April 24, 2015 1:43 AM

I too had the same problem on one of our machines - what I found is that I had to go though a number of different registry keys in HKEY_CLASSES_ROOT and modify all of them so they no longer pointed to the visio viewer. Once I had removed all instances pointing to viewer I found that it was then working again. Here is a list of my keys and their settings that got rid of the issue:

.vsd - (default) Visio.Drawing.11

        Content Type  application/vnd.visio

.vsl - (default) Visio.AddOn.11

        Content Type  application/vnd.visio

.vss - (default) Visio.Stencil.11

        Content Type  application/vnd.visio

.vst - (default) Visio.Template.11

        Content Type  application/vnd.visio

.vsu - (default) Visio.CustomUI.11

        Content Type  application/vnd.visio

.vsw - (default) Visio.Workspace.11

        Content Type  application/vnd.visio

.vsx - (default) Visio.Stencil.11

        Content Type  application/vnd.visio

.vtx - (default) Visio.Template.11

        Content Type  application/vnd.visio

I Hope this helps resolve the issue if like me the originally posted fix doesn't resolve the issue. Please remember that editing the registry is not to be done without understanding the risks involved & that if you're not careful you can cause irreversible damage to your system. As such I accept to no Liability for the information contained with this post.

• Proposed as answer by MDL2 Friday, April 24, 2015 1:43 AM

I have been beating my head against the wall for about a year with a VISIO 2007 start-up problem. VISIO ran fine when 1st installed, but at some point broke, triggering the Windows Configuration Installer, to run every time I opened VISIO 2007, from a .vsd drawing file or the VISIO.EXE. I also had prior installed Office 2010 Professional on the same Windows 7 SP1 machine. I tried all mentioned registry hacks and file associations mentioned in this and other threads, but nothing helped.

However the Windows Update titled "2007 Office System Update" KB2767916 dated February 12, 2013 was installed on my machine. I uninstalled this KB2767916 update and the problem is now [SOLVED]. The Windows Configuration Installer no longer tries to run and VISIO opens lightning quick, no matter if executing a .vsd  .vst or the VISIO.EXE, including the desktop shortcut. see the article below for a detailed description of this update. DO NOT INSTALL.

https://support2.microsoft.com/kb/2767916?wa=wsignin1.0

Tony

• Proposed as answer by Geekwadd Sunday, October 12, 2014 8:12 PM
• Edited by Geekwadd Sunday, October 12, 2014 8:23 PM

I have been beating my head against the wall for about a year with a VISIO 2007 start-up problem. VISIO ran fine when 1st installed, but at some point broke, triggering the Windows Configuration Installer, to run every time I opened VISIO 2007, from a .vsd drawing file or the VISIO.EXE. I also had prior installed Office 2010 Professional on the same Windows 7 SP1 machine. I tried all mentioned registry hacks and file associations mentioned in this and other threads, but nothing helped.

However the Windows Update titled "2007 Office System Update" KB2767916 dated February 12, 2013 was installed on my machine. I uninstalled this KB2767916 update and the problem is now [SOLVED]. The Windows Configuration Installer no longer tries to run and VISIO opens lightning quick, no matter if executing a .vsd  .vst or the VISIO.EXE, including the desktop shortcut. see the article below for a detailed description of this update. DO NOT INSTALL.

https://support2.microsoft.com/kb/2767916?wa=wsignin1.0

Tony

• Proposed as answer by Geekwadd Sunday, October 12, 2014 8:12 PM
• Edited by Geekwadd Sunday, October 12, 2014 8:23 PM

I have been beating my head against the wall for about a year with a VISIO 2007 start-up problem. VISIO ran fine when 1st installed, but at some point broke, triggering the Windows Configuration Installer, to run every time I opened VISIO 2007, from a .vsd drawing file or the VISIO.EXE. I also had prior installed Office 2010 Professional on the same Windows 7 SP1 machine. I tried all mentioned registry hacks and file associations mentioned in this and other threads, but nothing helped.

However the Windows Update titled "2007 Office System Update" KB2767916 dated February 12, 2013 was installed on my machine. I uninstalled this KB2767916 update and the problem is now [SOLVED]. The Windows Configuration Installer no longer tries to run and VISIO opens lightning quick, no matter if executing a .vsd  .vst or the VISIO.EXE, including the desktop shortcut. see the article below for a detailed description of this update. DO NOT INSTALL.

https://support2.microsoft.com/kb/2767916?wa=wsignin1.0

Tony

• Proposed as answer by Geekwadd Sunday, October 12, 2014 8:12 PM
• Edited by Geekwadd Sunday, October 12, 2014 8:23 PM

I didn't bother giving this a shot because not everyone sits around on their corporate network with the ability to create new accounts in ADU&C and make them members of the Domain Admins group. For those like me who only have local admin rights available to solve this problem, the registry fix posted by stuart_b is a much better solution. It takes a flawed solution posted by Microsoft under KB 2685120 and expands upon it to include other registry values that must be changed to be rid of "Please wait while Windows configures Microsoft Visio..." for good!

I too had the same problem on one of our machines - what I found is that I had to go though a number of different registry keys in HKEY_CLASSES_ROOT and modify all of them so they no longer pointed to the visio viewer. Once I had removed all instances pointing to viewer I found that it was then working again. Here is a list of my keys and their settings that got rid of the issue:

.vsd - (default) Visio.Drawing.11

        Content Type  application/vnd.visio

.vsl - (default) Visio.AddOn.11

        Content Type  application/vnd.visio

.vss - (default) Visio.Stencil.11

        Content Type  application/vnd.visio

.vst - (default) Visio.Template.11

        Content Type  application/vnd.visio

.vsu - (default) Visio.CustomUI.11

        Content Type  application/vnd.visio

.vsw - (default) Visio.Workspace.11

        Content Type  application/vnd.visio

.vsx - (default) Visio.Stencil.11

        Content Type  application/vnd.visio

.vtx - (default) Visio.Template.11

        Content Type  application/vnd.visio

I Hope this helps resolve the issue if like me the originally posted fix doesn't resolve the issue. Please remember that editing the registry is not to be done without understanding the risks involved & that if you're not careful you can cause irreversible damage to your system. As such I accept to no Liability for the information contained with this post.

This fixed the problem for me. Thank you stuart_b!

This ended up not being the issue for me. That update wasn't on my system. Hopefully it'll help someone else. The registry fix worked great and seems to be the best solution for anyone who had the Visio Viewer installed prior to installing the full version of Visio.

Great thank you, this worked for me

"However the Windows Update titled "2007 Office System Update" KB2767916 dated February 12, 2013 was installed on my machine. I uninstalled this KB2767916 update and the problem is now [SOLVED]."

This is what fixed the problem for me under Win7 32bit.

Thank you for sharing this. This solved my problem and Visio 2007 is now starting up like a charm.

I tried the registry solution mentioned above...it didn't help.   So, I tried uninstalling the System Update:  KB2767916.   It worked....this actually fixed the problem.   Thanks for sharing!